src/pages/[section]/[page]/[tab].astro (1)

33-44: Move the apiOnly check before fetching collections to avoid unnecessary work.

When PF_API_ONLY is 'true', collections are fetched via Promise.all and then immediately discarded. Move the early return to the top of getStaticPaths() to skip the async operations entirely.

♻️ Proposed optimization

 export async function getStaticPaths() {
+  if (process.env.PF_API_ONLY === 'true') {
+    return []
+  }
+
   const collections = await Promise.all(
     content.map(
       async (entry) => await getCollection(entry.name as 'textContent'),
     ),
   )
-
-  const apiOnly = process.env.PF_API_ONLY === 'true'
-
-  if (apiOnly) {
-    return []
-  }

   const flatCol = collections

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/pages/`[section]/[page]/[tab].astro around lines 33 - 44, In
getStaticPaths(), check the apiOnly flag (process.env.PF_API_ONLY === 'true')
and return [] before starting the Promise.all that maps over content and calls
getCollection; specifically move the apiOnly check to the top of the
getStaticPaths function so you avoid invoking content.map, getCollection, and
Promise.all when apiOnly is true.

src/pages/[section]/[...page].astro (1)

32-43: Move the apiOnly check before fetching collections.

Same issue as in [tab].astro — the collections are fetched before checking PF_API_ONLY, wasting async work when API-only mode is enabled.

♻️ Proposed optimization

 export async function getStaticPaths() {
+  if (process.env.PF_API_ONLY === 'true') {
+    return []
+  }
+
   const collections = await Promise.all(
     content.map(
       async (entry) => await getCollection(entry.name as 'textContent'),
     ),
   )
-
-  const apiOnly = process.env.PF_API_ONLY === 'true'
-
-  if (apiOnly) {
-    return []
-  }

   return collections.flat().map((entry) => {

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/pages/`[section]/[...page].astro around lines 32 - 43, In getStaticPaths,
check PF_API_ONLY early and return if true before starting any async work: move
the apiOnly (const apiOnly = process.env.PF_API_ONLY === 'true') check to the
top of the function and return [] immediately when true so you avoid calling
getCollection or iterating over content; update references to content and
getCollection accordingly to only run when not in API-only mode.

cli/cli.ts (1)

198-198: Clarify the option description.

The description says "skip standalone content pages" but based on the implementation, ALL content pages (both [section]/[...page].astro and [section]/[page]/[tab].astro) are skipped when this flag is set. Consider updating the description to be more accurate.

📝 Suggested clarification

-program.option('--api-only', 'only build API and component pages, skip standalone content pages', false)
+program.option('--api-only', 'only build API routes, skip all content pages', false)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@cli/cli.ts` at line 198, The --api-only option description is misleading:
update the program.option call for '--api-only' (in cli.ts where program.option
is defined) to state that it skips all content pages (both standalone and nested
content routes such as [section]/[...page].astro and
[section]/[page]/[tab].astro), not just "standalone" pages; keep the same flag
name and default value but change the human-readable description to accurately
reflect that all content pages are omitted when this flag is set.